In SAS^® Merchandise Allocation, the release process might create an incorrect release file for MICPGROUP definitions when multi-threading is enabled during the import process. The issue occurs only for a specific scenario, as explained below.

Data for the release file is written incorrectly when both of these conditions are true:

• You send two or more import files simultaneously.
• The sequential order of the child definition fits into a different parent.

Example:

Parent = 655
Child = 657
Child = 659

Parent = 656
Child = 658
Child = 661

Note: Child 658 is in the second parent in the example above. However, it falls between the two child definitions in the first parent.

To work around this issue, set the batchimport.concurrent.request.count parameter to 1. This parameter specifies the number of threads that is to be used for concurrent processing.  When the parameter is set to 1, multi-threading is not used.

A hot fix is planned for this issue.

Operating System and Release Information